Skip to main content

Alarm Rules

Overview​

ThingsIoT provides a built-in device alarm function that allows you to create a variety of alarm rules according to actual business requirements. When a device property changes abnormally or no data is reported for an extended period, the platform can automatically trigger an alarm, update the device's alarm status, generate an alarm message, and notify relevant personnel through multiple channels.

Before using device alarms, review the following core concepts:

  • Alarm Rule
    Created by project members to define the conditions under which a device alarm is triggered or cleared and the recipients who should be notified. Multiple alarm rules can be configured for each device to cover different monitoring requirements.
  • Alarm Status
    Indicates whether the device is currently in an alarm condition. The status is pushed in real time according to each rule's trigger conditions, allowing users to quickly determine whether device operation is abnormal.
  • Alarm Notification
    Based on the alarm-rule configuration, the platform can automatically send alarm messages to external recipients through email, SMS, phone, webhook, and other channels, ensuring that relevant personnel can learn about and respond to abnormal conditions immediately.
  • Alarm Message
    When a device triggers or clears an alarm rule, the platform generates an alarm message and records it in Alarm History. Historical records can be used to trace the time, type, and handling status of each event.

Quick Start​

Alarm Rules​

Create an alarm rule for the current device under Device Details > Alarms > Alarm Rules, as shown below.

Alarm Types​

1. Device Property Change

An alarm notification can be triggered when a device property value changes.

Note: The default alarm silence period is five minutes.

1. Assume that the device acquisition interval is 10 minutes and the alarm silence period is set to one minute. The first alarm is triggered and pushed immediately at 8:00. A second alarm can be pushed only after the next polling cycle, provided that the device remains in the alarm state, at 8:10.

2. Assume that the acquisition interval is one minute and the alarm silence period is five minutes. The first alarm is pushed immediately at 8:00, and the next notification is pushed at 8:05.

2. Property Activity Monitoring

When a device property has not been updated within the period defined by the monitoring policy, the platform triggers an alarm notification. This function can be used to detect offline devices.

Note: The default acquisition cycle is five minutes.

1. Acquisition cycle: the upload interval configured in the configuration tool, meaning how frequently the data point uploads data to the platform.

2. Monitoring policy: Conservative mode allows a certain amount of data delay and reduces false alarms; Balanced mode is the recommended default; Aggressive mode detects disconnections more quickly but may produce false alarms. The system intelligently adjusts alarm notifications according to the acquisition cycle and monitoring policy.

Filter Conditions​

Filter conditions are an important part of an alarm rule. The platform supports conditions such as greater than, less than, within a range, and outside a range.

Alarm Severity​

Alarm severity distinguishes the importance of an alarm and is displayed in Alarm History and alarm notifications. For example, when email notifications are used, the alarm severity appears in the email content.

Available alarm severities include:

  • General Alarm
  • Major Alarm
  • Critical Alarm

Alarm Notifications​

Notification Groups​

Alarm rules are associated with notification groups that send alarm notifications. Notification groups must be created in advance. One alarm rule can be associated with multiple notification groups, allowing different personnel to receive different types of alarm information.

Supported notification types include:

  • Email
  • SMS
  • WeCom
  • Webhook

Notes:

Notifications are pushed when the value changes. For the same notification type, a message is sent only when the value changes, helping conserve notification credits.

Although a notification group is contacted only when the value changes, every alarm event is still recorded in Alarm History.

Due to carrier restrictions, some messages may be blocked. Check delivery status when necessary. The same phone number can receive no more than 50 SMS messages per day by default, although an adjustment may be requested. Identical SMS content sent to the same phone number must be separated by more than 60 seconds.

Alarm Messages​

Alarm History​

Whenever the status of a device alarm rule changes, the platform records an alarm message. A summary is also displayed in the alarm-count section on the home page.